Repository navigation
ci: publish with changesets/action v2 so releases get tags again - #25
Conversation
@changesets/cli v3 no longer prints the "New tag:" lines that changesets/action v1 parsed, so the 2.2.0 run published to npm but skipped the git tag and GitHub release (both were created by hand afterwards). Action v2 reads the CHANGESETS_OUTPUT file instead and renames the inputs to version-script, publish-script and github-token (which defaults to the workflow token).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The publish workflow’s script handoff and token permissions match the v2 action contract. No material merge-blocking risk is established. Pre-merge checks |
|
Why
cliuno@2.2.0reached npm, but the Publish run never pushed av2.2.0tag or opened a GitHub release.@changesets/clito v3. v3'schangeset publishno longer prints theNew tag: v…lines thatchangesets/action@v1parses.New tag: v2.1.1and thengit push origin v2.1.1.I created the
v2.2.0tag and release by hand, on the Version Packages commit242dc80.Change
changesets/action@v2, the release line built for CLI v3. It reads what was published from theCHANGESETS_OUTPUTfile, whichchangeset publishinsidescripts/ci-publish.shwrites because the script inherits the env.GITHUB_TOKENenv var:version→version-scriptpublish→publish-scriptgithub-tokendefaults to the workflow token.ci-publish.shguard against re-publishing, and the Version Packages PR flow.Testing
publish.ymlandmain.yml.ci-publish.sh. v2 allows a custom publish script that writes no output file and only logs a warning.Summary by CodeRabbit